Skip to content

Conversation

@shanmugamr1992
Copy link
Contributor

What does this PR do ?

⚠️ For major changes (either in lines of code or in its impact), please make sure to first share discuss a design-doc with the team.

Contribution process

flowchart LR
    A[Pre-checks] --> B[PR Tests]
    subgraph Code Review/Approval
        C1[Expert Review] --> C2[Final Review]
    end
    B --> C1
    C2 --> D[Merge]
Loading

Pre-checks

  • I want this PR in a versioned release and have added the appropriate Milestone (e.g., Core 0.8)
  • I have added relevant unit tests
  • I have added relevant functional tests
  • I have added proper typing to my code Typing guidelines
  • I have added relevant documentation
  • I have run the autoformatter.sh on my PR

Code review

The following process is enforced via the CODEOWNERS file for changes into megatron/core. For changes outside of megatron/core, it is up to the PR author whether or not to tag the Final Reviewer team.

For MRs into `main` branch

(Step 1): Add PR label Expert Review

(Step 2): Collect the expert reviewers reviews

  1. Attach the Expert Review label when your PR is ready for review.
  2. GitHub auto-assigns expert reviewers based on your changes. They will get notified and pick up your PR soon.

⚠️ Only proceed to the next step once all reviewers have approved, merge-conflict are resolved and the CI is passing.
Final Review might get declined if these requirements are not fulfilled.

(Step 3): Final Review

  1. Add Final Review label
  2. GitHub auto-assigns final reviewers based on your changes. They will get notified and pick up your PR soon.

(Optional Step 4): Cherry-pick into release branch

If this PR also needs to be merged into core_r* release branches, after this PR has been merged, select Cherry-pick to open a new PR into the release branch.

For MRs into `dev` branch The proposed review process for `dev` branch is under active discussion.

MRs are mergable after one approval by either [email protected] or [email protected].

Merging your PR

Any member of core-adlr and core-nemo will be able to merge your PR.

@shanmugamr1992 shanmugamr1992 requested a review from a team as a code owner November 15, 2025 00:01
@copy-pr-bot
Copy link

copy-pr-bot bot commented Nov 15, 2025

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@kvareddy kvareddy requested a review from tdene November 15, 2025 06:52
@ko3n1g ko3n1g requested review from a team as code owners November 15, 2025 17:09
@tdene tdene mentioned this pull request Nov 17, 2025
6 tasks
@kvareddy
Copy link
Contributor

@santhnm2 can you please take a look at this MR?

@tdene
Copy link
Contributor

tdene commented Nov 22, 2025

I left a few nit comments, but the general code looks good to me.

I will approve this after main is merged into it.

@shanmugamr1992
Copy link
Contributor Author

/ok

@shanmugamr1992
Copy link
Contributor Author

/ok to test 300c130

@shanmugamr1992
Copy link
Contributor Author

/ok to test 4303dd0

@shanmugamr1992
Copy link
Contributor Author

/ok to test 0740fd6

@shanmugamr1992 shanmugamr1992 added this pull request to the merge queue Nov 25, 2025
Merged via the queue into NVIDIA:main with commit 898d633 Nov 25, 2025
127 checks passed
@shanmugamr1992 shanmugamr1992 deleted the dynamic_latest branch November 25, 2025 22:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants